The latest Buf updates on your PR. Results from workflow CI / buf-check (pull_request).

Claude finished @julienrbrt's task in 1m 1s —— View job

Code Review: chore: remove replaces from ev-node

• Gather context and read changed files
• Analyze go.mod changes
• Provide review feedback

Summary

This PR removes three replace directives from go.mod that were pinning all google.golang.org/genproto variants to an older fixed version (v0.0.0-20240213162025-012b6fc9bca9), along with the direct dependency on the base google.golang.org/genproto package.

Changes

go.mod — Removes:

1. The google.golang.org/genproto entry from require (the root package, not the sub-packages)
2. The replace block that pinned all three genproto modules to a single older version

go.sum — The bulk of the diff (-977/+11): removing checksums for many transitive historical cloud.google.com/go .mod entries that were only pulled in by the old pinned genproto version.

Review

Correctness ✅

The original replace block was a workaround for an old issue where different transitive dependencies pulled in incompatible genproto versions, causing ambiguous import errors. Removing these replaces means the Go module resolver will now pick the version determined by the dependency graph — in this case v0.0.0-20260209200024-4cfbd4190f57, which is significantly newer than the old pinned version (v0.0.0-20240213162025-012b6fc9bca9). This is the correct approach once the upstream ecosystem has settled on consistent versioning.

go.sum cleanup ✅

The 977 deletions in go.sum are expected and clean — they represent checksum entries for old indirect cloud.google.com/go module versions that were only needed to satisfy the old pinned genproto. These are purely go.mod hash entries (not source code checksums), so their removal has no runtime impact.

Risk ✅ Low

• The buf-check CI workflow has passed, confirming protobuf-related consistency
• No application logic is changed; this is purely a dependency management cleanup
• The sub-packages (googleapis/api, googleapis/rpc) that are actually used remain in require

Minor observation — worth confirming that the full test suite (just test / just test-integration) passes after this change, since removing replace directives can occasionally surface version skew issues at compile time. If CI is green across all jobs, this is ready to merge.

Overall: LGTM. Clean dependency hygiene — removing workaround replace pins in favor of proper module resolution is the right long-term approach.

No actionable comments were generated in the recent review. 🎉

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.20%. Comparing base (abb6b71) to head (323c300).
⚠️ Report is 1 commits behind head on main.

@@           Coverage Diff           @@
##             main    #3158   +/-   ##
=======================================
  Coverage   60.20%   60.20%           
=======================================
  Files         115      115           
  Lines       11896    11896           
=======================================
  Hits         7162     7162           
  Misses       3923     3923           
  Partials      811      811           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.